Cool ice service handler

ABSTRACT

An apparatus for and method of utilizing an internet terminal coupled to the world wide web to access an existing proprietary data base management system having a dialog-based request format. The user request is received by a web server from the world wide web and converted into an object consisting of one or more sequenced data base management commands. An expiration date corresponding to the object is checked. If the object is obsolete, a diagnostic message is sent to the requester. Otherwise the data base management commands are sequentially presented to the data base management system and the intermediate products stored. After all of the sequenced data base management commands have been executed, the web server combines the intermediate products to form a complete response to the initial user request. An MIME type is accessed from a storage facility and appended to the complete response. The response containing the MIME type is transferred to the user over the world wide web.

CROSS REFERENCE TO CO-PENDING APPLICATIONS

U.S. patent application Ser. No. 09/164,759, filed Oct. 1, 1998 andentitled, “A Common Gateway Which Allows Applets to Make Program Callsto OLTP Applications Executing on an Enterprise Server”; U.S. patentapplication Ser. No. 09/164,932, filed Oct. 1, 1998 and entitled, “AMulti-Client User Customized DOM Gateway for an OLTP Enterprise ServerApplication”; U.S. patent application Ser. No. 09/164,908, filed Oct. 1,1998 and entitled, “An Automated Development System for DevelopingApplications that Interface with Both Distributed Component Object Model(DOM) and Enterprise Server Environments”; U.S. patent application Ser.No. 09/164,933, filed Oct. 1, 1998, and entitled, “Providing a ModularGateway Architecture Which Isolates Attributes of the Client and ServerSystems into Independent Components”; U.S. patent application Ser. No.09/164,822, filed Oct. 1, 1998, and entitled, “Making CGI Variables andCookie Information Available to an OLTP System”; U.S. patent applicationSer. No. 09/164,673, filed Oct. 1, 1998, and entitled, “A Gateway forDynamically Providing Web Site Status Information”; U.S. patentapplication Ser. No. 09/164,750, filed Oct. 1, 1998, and entitled,“Development System for Automatically Enabling a Server Application toExecute with an XATMI-complaint transaction MGR: Managing Transactionswithin Multiple Environments”; U.S. patent application Ser. No.09/189,053, filed Nov. 9, 1998 and entitled, “Cool ICE Batch Interface”;U.S. patent application Ser. No. 09/189,381, filed Nov. 9, 1998, andentitled, “Cool ICE Debug”; U.S. patent application Ser. No. 09/188,628,filed Nov. 9, 1998, and entitled, “Cool ICE Workstation Directory/FileBrowser”; U.S. patent application Ser. No. 09/188,849, filed Nov. 9,1998, and entitled, “Cool ICE Icons”; U.S. patent application Ser. No.09/189,383, filed Nov. 9, 1998 and entitled, “Cool ICE ServiceTemplates”; U.S. patent application Ser. No. 09/189,615, filed Nov. 9,1998, and entitled, “Availability Message”; U.S. patent application Ser.No. 09/189,617, filed Nov. 9, 1998, and entitled, “Cool ICE SystemSettings”; U.S. patent application Ser. No. 09/188,725, filed Nov. 9,1998, and entitled, “Cool ICE State Management”; and U.S. patentapplication Ser. No. 09/189,616, filed Nov. 9, 1998, and entitled,“Server Side Variables” are commonly assigned co-pending applicationsincorporated herein by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention generally relates to data base management systemsand more particularly relates to enhancements for providing access todata base management systems via internet user terminals.

2. Description of the Prior Art

Data base management systems are well known in the data processing art.Such commercial systems have been in general use for more than 20 years.One of the most successful data base management systems is availablefrom Unisys Corporation and is called the Classic MAPPER® data basemanagement system. The Classic MAPPER system can be reviewed using theClassic MAPPER User's Guide which may be obtained from UnisysCorporation.

The Classic MAPPER system, which runs on proprietary hardware alsoavailable from Unisys Corporation, provides a way for clients topartition data bases into structures called filing cabinets and drawers,as a way to offer a more tangible format. The Mapper data base managerutilizes various predefined high-level instructions whereby the database user may manipulate the data base to generate human-readable datapresentations called “reports”. The user is permitted to prepare listsof the various predefined high-level instructions into data base managerprograms called “Mapper Runs”:. Thus, users of the Classic MAPPER systemmay create, modify, and add to a given data base and also generateperiodic and aperiodic reports using various Mapper Runs.

However, with the Classic MAPPER system, as well as with similarproprietary data base management systems, the user must interface withthe data base using a terminal coupled directly to the proprietarysystem and must access and manipulate the data using the Mapper Runcommand language of Classic MAPPER. Ordinarily, that means that the usermust either be co-located with the hardware which hosts the data basemanagement system or must be coupled to that hardware through dedicatedtelephone, satellite, or other data links. Furthermore, the user usuallyneeds to be schooled in the command language of Classic MAPPER (or otherproprietary data base management system) to be capable of generatingMapper Runs.

Since the advent of large scale, dedicated, proprietary data basemanagement systems, the internet or world wide web has come into being.Unlike closed proprietary data base management systems, the internet hasbecome a world wide bulletin board, permitting all to achieve nearlyequal access using a wide variety of hardware, software, andcommunication protocols. Even though some standardization has developed,one of the important characteristics of the world wide web is itsability to constantly accept new and emerging techniques within a globalframework. Many current users of the internet have utilized severalgenerations of hardware and software from a wide variety of suppliersfrom all over the world. It is not uncommon for current day youngchildren to have ready access to the world wide web and to havesubstantial experience in data access using the internet.

Thus, the major advantage of the internet is its universality. Nearlyanyone, anywhere can become a user. That means that virtually allpersons are potentially internet users without the need for specializedtraining and/or proprietary hardware and software. One can readily seethat providing access to a proprietary data base management system, suchas Classic MAPPER, through the internet would yield an extremelyinexpensive and universally available means for accessing the data whichit contains and such access would be without the need for considerablespecialized training.

There are several basic problems with permitting internet access to aproprietary data base. The first is a matter of security. Because theinternet is basically a means to publish information, great care must betaken to avoid intentional or inadvertent access to certain data byunauthorized internet users. In practice this is substantiallycomplicated by the need to provide various levels of authorization tointernet users to take full advantage of the technique. For example, onemight have a first level involving no special security featuresavailable to any internet user. A second level might be for specificcustomers, whereas a third level might be authorized only for employees.One or more fourth levels of security might be available for officers orothers having specialized data access needs.

Existing data base managers have security systems, of course. However,because of the physical security with a proprietary system, a certaindegree of security is inherent in the limited access. On the other hand,access via the internet is virtually unlimited which makes the securityissue much more acute.

The second major problem is imposed by the internet protocol itself. Oneof the characteristics of the internet which makes it so universal isthat any single transaction in HTML language combines a single transfer(or request) from a user coupled with a single response from theinternet server. In general, there is no means for linking multipletransfers (or requests) and multiple responses. In this manner, theinternet utilizes a transaction model which may be referred to as“stateless”. This limitation ensures that the internet, its users, andits servers remain sufficiently independent during operation that no oneentity or group of entities can unduly delay or “hang-up” thecommunications system or any of its major components. Each transmissionsresults in a termination of the transaction. Thus, there is no generalpurpose means to link data from one internet transaction to another,even though in certain specialized applications limited amounts of datamay be coupled using “cookies” or via attaching data to a specific HTMLscreen.

However, some of the most powerful data base management functions orservices of necessity rely on coupling data from one transaction toanother in dialog fashion. In fact this linking is of the essence ofMapper Runs which assume change of state from one command languagestatement to the next. True statelessness from a first Mapper command tothe next or subsequent Mapper command would preclude much of the powerof Classic MAPPER (or any other modern data base management system) as adata base management tool and would eliminate data base management as wenow know it.

It is readily appreciated that communication between the internet userterminal and the server hosting the Cool ICE data base management systemis through the use of HTML display pages, whereas the internalcommunication within the server is not. A standard technique foridentification of an object type within the HTML protocol is through theuse of MIME type. This standard readily identifies the type of object(e.g., text, audio, video, graphics, etc.). However, the MIME type istypically not used with existing proprietary data base managementsystems and is not used at all with Classic MAPPER system. Therefore, aproblem exists with the transfer of objects from the server to theinternet terminal without the MIME type to identify the nature of thedata.

SUMMARY OF THE INVENTION

The present invention overcomes the disadvantages of the prior art byproviding a method of and apparatus for utilizing the power of a fullfeatured data base management system by a user at a terminal coupled tothe world wide web or internet. In order to permit any such access, thepresent invention must first provide a user interface, called a gateway,which translates transaction data transferred from the user over theinternet in HTML format into a format from which data base managementsystem commands and inputs may be generated. The gateway must alsoconvert the data base management system responses and outputs into anHTML document for display on the user's internet terminal. Thus, as aminimum, the gateway must make these format and protocol conversions. Inthe preferred embodiment, the gateway resides in the web server coupledto the user via the world wide web and coupled to proprietary data basemanagement system.

To make access to a proprietary data base by internet users practical, asophisticated security system is required to prevent intentional orinadvertent unauthorized accesses. As discussed above, such a securitysystem should provide multiple levels of access to accommodate a varietyof authorized user categories. In the preferred embodiment of thepresent invention, several levels of data classification are providedand several classes of users are defined. This permits certain levels ofdata to be accessed by one or more of the several classes of user. Thesecurity system may either reside in the web server containing thegateway or may be an existing component of the data base managementsystem.

Whereas the gateway and the security system are the minimum necessary topermit the most rudimentary form of communication between the internetterminal of the user and the proprietary data base management system, asexplained above, the internet is a “stateless” communication system; theaddition of the gateway and the security system do not change thisstatelessness. To unleash the real power of the data base managementsystem, the communication protocol between the data base and the userrequires functional interaction between the various data transfers.

The present invention adds state management to this environment. Insteadof considering each transfer from the internet user coupled with thecorresponding server response as an isolated transaction event asdefined by the world wide web, one or more related service requests maybe functionally associated in a service request sequence as defined bythe data base management system into a dialog.

A repository is established to store the state of the service requestsequence. As such, the repository can store intermediate requests andresponses, as well as other data associated with the service requestsequence. Thus, the repository buffers commands, data, and intermediateproducts utilized in formatting subsequent data base management servicerequests and in formatting subsequent HTML pages to be displayed to theuser.

The transaction data in HTML format received by the server from theuser, along with the state information stored in the repository, areprocessed by a service handler into a sequence of service requests inthe command language of the data base management system. Sequencing andcontrol of the data base management system is via an administrationmodule.

Through the use of the repository to store the state of the servicerequest sequence, the service handler to generate data base managementcommand language, and the administration module, the world wide web useris capable of performing each and every data base management functionavailable to any user, including a user from a proprietary terminalhaving a dedicated communication link which is co-located with theproprietary data base management system hardware and software. Inaddition, the data base management system user at the world wide webterminal is able to accomplish this in the HTML protocol, withoutextensive training concerning the command language of the data basemanagement system.

The data transfers between the internet user terminals and the server isthrough HTML display pages. It is conventional to describe the data typeof an HTML object through a standardized MIME type code. The preferredmode of the present invention preserves MIME type codes for objectsreceived in HTML and synthesizes MIME type codes for objects created inother formats. The stored and/or synthesized MIME type code istransmitted along with HTML display pages in transfers from the serverto an internet terminal.

In addition, the service handler facilities which maintain the MIME typecode are also useful to store an expiration date, if any, associatedwith a particular object. Using the expiration date feature enables theserver to automatically inhibit transmission of obsolete objects.

BRIEF DESCRIPTION OF THE DRAWINGS

Other objects of the present invention and many of the attendantadvantages of the present invention will be readily appreciated as thesame becomes better understood by reference to the following detaileddescription when considered in connection with the accompanyingdrawings, in which like reference numerals designate like partsthroughout the figures thereof and wherein:

FIG. 1 is pictographic view of the Cool ICE system coupled between auser on the world wide web and an existing proprietary data basemanagement system;

FIG. 2 is a schematic drawing showing the operation of a multi-levelsecurity system in accordance with the preferred embodiment of thepresent invention;

FIG. 3 is a pictographic view of the hardware of the preferredembodiment;

FIG. 4 is a semi-schematic diagram of the operation of the Cool ICEsystem;

FIG. 5 is an overall schematic view of the software of the Cool ICEsystem;

FIG. 6 is a schematic view of a service request;

FIG. 7 shows a schematic view of a service request sequence;

FIG. 8 is a diagrammatic comparison between a dialog-based structure anda service-based structure;

FIG. 9 is a detailed diagram of the storage and utilization of stateinformation within the repository;

FIG. 10 is a diagram showing storage of information associated with MIMEtype and expiration date;

FIG. 11 is a diagram showing utilization of information associated withMIME type and expiration date; and

FIG. 12 is a detailed diagram showing how the MIME type and expirationdate information are used in communication with an internet terminal.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The present invention is described in accordance with several preferredembodiments which are to be viewed as illustrative without beinglimiting. These several preferred embodiments are based upon Series 2200hardware and operating systems, the Classic MAPPER data base managementsystem, and the Cool ICE software components, all available from UnisysCorporation.

FIG. 1 is an overall pictographic representation of a system 10permitting access to a proprietary data base management system via aninternet terminal. Existing data bases and applications 12 representscommercially available hardware and software systems which typicallyprovide select users with access to proprietary data and data basemanagement functions. In the preferred embodiment, existing data basesand applications 12 represents Series 2200 hardware and operating systemcontaining one or more data bases prepared using Classic MAPPER database management system, all available from Unisys Corporation.Historically, existing data bases and applications 12 could only beaccessed from a dedicated, direct terminal link, either physicallyco-located with the other system elements or connected thereto via asecured dedicated telephonic, satellite, or fiber optic link.

With the preferred mode of the present invention, communication betweennew web application terminal 14 and existing data bases and applications12 is facilitated. As discussed above, this permits nearly universalaccess by users world wide without specialized hardware and/or usertraining. The user effects the access using standardized HTMLtransaction language through world wide web link 16 to the Cool ICEsystem 20, which serves as a world wide web server to world wide weblink 16.

Cool ICE system 20 appears to existing data bases and applications 12 asa data base management system proprietary user terminal over dedicatedlink 18. Oftentimes, dedicated link 18 is an intranet or other localizednetwork link. Cool ICE system 20 is currently available in commercialform without the present invention as Cool ICE Revision Level 1.1 fromUnisys Corporation.

FIG. 2 is a schematic diagram of security system 22 of the preferredmode of the present invention. By way of example, there are fourcategories of service defined, each with its own functionality andportion of the data base. Service A 36 contains data and functions whichshould only be made available to customers. Service B 38 contains dataand functions which should only be made available to customers oremployees. Service C 40 contains data and functions which should only bemade available to employees, and Service D 42, containing the leastrestrictive data and functions may be made available to anyone,including the general public.

In a typical application, Service D 42 might contain the general homepage information of the enterprise. It will consist of only the mostpublic of information. It is likely to include the name, address, e-mailaddress, and phone number of the enterprise, along with the most publicof the business details. Usually, Service D 42 would include means ofpresenting the information in a sufficiently interesting way to enticethe most casual of the public user to make further inquiry and thusbecome more involved with the objectives of the enterprise. Service D 42represents the lowest level of security with data and functionsavailable to all.

Service C 40 is potentially the highest level of classification. Itcontains data and functions which can be made available only toemployees. In actual practice, this might entail a number of sub levelscorresponding to the various levels of authority of the variousemployees. However, some services may be so sensitive that theenterprise decides not to provide any access via the internet. Thismight include such things as strategic planning data and tools, advancedfinancial predictions, specific information regarding individualemployees, marketing plans, etc. The penalty for this extreme securitymeasure is that even authorized individuals are prohibited fromaccessing these services via the internet, and they must take thetrouble to achieve access via an old-fashioned dedicated link.

Customers and employees may share access to Service B 38. Nevertheless,these data and functions are sufficiently sensitive that they are notmade public. Service B 38 likely provides access to productspecifications, delivery schedules and quantities, and pricing.

For customer access only is Service A 36. One would expect marketinginformation, along with specific account information, to be availablehere.

These four service levels (i.e., Service A 36, Service B 38, Service C40, and Service D 42) are regulated in accordance with three securityprofiles. The lowest level of security does not require a securityprofile, because any member of the general public may be granted access.This can be readily seen as guest category 28 (e.g., a member of thepublic) can directly access Service D 42. Of course, all othercategories of user may also directly access Service D 42, because allmembers of the more restrictive categories (e.g., customers andemployees) are also members of the general public (i.e., the leastrestrictive category).

Security Profile #1, 30 permits access to Service A 36 if and only ifthe requestor seeking access is a customer and therefore a member ofcustomer category 24. Members of customer category 24 need to identifythemselves with a customer identification code in order to gain access.The assigning and processing of such identification codes are well knownto those of skill in the art.

Similarly, Security Profile #3, 34 permits access to Service C 40 if andonly if the requester seeking access is an employee and therefore amember of employee category 26. Security Profile #2, 32 permits accessto Service B 38 to requestors from either customer category 24 oremployee category 26, upon receipt of a customer identification code oran employee identification code.

FIG. 3 is a pictorial diagram of hardware suite 44 of the preferredembodiment of the present invention. The client interfaces with thesystem via internet terminal 46. Preferably, internet terminal 46 is anindustry compatible, personalized computer having a current version ofthe Windows operating system and suitable web browser, all being readilyavailable commercial products. Internet terminal 46 communicates overworld wide web access 48 using standardized HTML protocol.

The Cool ICE system is resident in web server 50, which is coupled tointernet terminal 46 via world wide web access 48. In the preferredmode, web server 50 is owned and operated by the enterprise owning andcontrolling the proprietary data base management system. Web server 50may serve as the internet access provider for internet terminal 46wherein world wide web access 48 is typically a dial-up telephone line.This would ordinarily be the case if the shown client were an employeeof the enterprise. On the other hand, web server 50 may be a remoteserver site on the internet if the shown client has a different internetaccess provider. This would ordinarily occur if the shown client were acustomer or guest.

In addition to being coupled to world wide web access 48, web server 50,containing the Cool ICE system, is coupled to intranet 52 of theenterprise as shown. Intranet 52 provides the enterprise withcommunication for its internal business purposes. This communication isadministered and managed by enterprise server 54 having enterpriseserver storage facility 56. Thus, employees and others granted accessmay communicate via intranet 52 within the physical security provided bythe enterprise.

Also coupled to intranet 52 is departmental server 58 havingdepartmental server storage facility 60. Additional departmental servers(not shown) may be coupled to intranet 52. The enterprise data andenterprise data base management service functionality typically resideswithin enterprise server 54, departmental server 58, and any otherdepartmental servers (not shown). Normal operation in accordance withthe prior art would provide access to this data and data base managementfunctionality via intranet 52 to users directly coupled to intranet 52.

In the preferred mode of the present invention, access to this data anddata base management functionality is also provided to users (e.g.,internet terminal 46) not directly coupled to intranet 52, butindirectly coupled to intranet 52 via web server 50. As explained belowin more detail, web server 50 provides this access utilizing the CoolICE system resident in web server 50.

FIG. 4 is pictographic view of the system of FIG. 3 with particulardetail showing the organization and operation of the Cool ICE system 62,which is resident in the web server (see also FIG. 3). In this view, theclient accesses the data base management system within the enterprisevia internet terminal 54 which is coupled to the web server 68 by worldwide web path 66. Again, the internet terminal 54 is preferably anindustry standard computer utilizing a commercially available webbrowser.

The basic request/response format of the Cool ICE system involves a“service” (defined in greater detail below) which is an object of theCool ICE system. The service is a predefined operation or relatedsequence of operations which provide the client with a desired static ordynamic result. The services are categorized by the language in whichthey were developed. Whereas all services are developed with client-sidescripting which is compatible with internet terminal 54 (e.g., HTML),the server-side scripting defines the service category. Native servicesutilize Cool ICE script for all server-side scripting. On the otherhand, open services may have server-side scripting in a variety ofcommon commercial languages including Jscript, VBScript, ActiveXcontrols, and HTML. Because native services are developed in the CoolICE language, greater development flexibility and variety are availablewith this technique.

Web server 68 provides open server processor 70 for Active Server Pages(ASP's) which have been developed as open services and Default ASPprocessor 72 for native services. After the appropriate decoding (i.e.,native or open service), a call to the corresponding Cool ICE object 74is initiated as shown. The selected object is processed by Cool ICEengine 76.

Repository 80 is a storage resource for long term storage of the CoolICE objects and short term storage of the state of a particular service.Further details concerning repository 80 may be found by consulting theabove referenced, commonly-assigned, co-pending U.S. patent application.In the preferred mode of the present invention, the objects stored inrepository 80 are typically very similar to mapper runs as describedabove. For a more detailed description of mapper runs, Classic MAPPERUser Manual is available from Unisys Corporation and incorporated hereinby reference. In the more general case, repository 80 would typicallystore predefined sequences of statements in the command language of theenterprise data base management system(s) to be accessed.

Cool ICE engine 76 sequences these previously stored command statementsand uses them to communicate via intranet 84 with the data basemanagement system(s) (e.g., Classic Mapper) resident on enterpriseserver 86 and departmental server 88. The short term storage capabilityof repository 80 is utilized by Cool ICE engine 76 to store the stateand intermediate products of each service until the processing sequencehas been completed. Following completion, Cool ICE engine 76 retrievesthe intermediate products from repository 80 and formats the outputresponse to the client, which is transferred to internet terminal 54 viaweb server 68 and world wide web path 66.

Cool ICE Administrator 82 is available for coordination of the operationof Cool ICE system 62 and thus can resolve conflicts, set run-timepriorities, deal with security issues, and serve as a developmentalresource. Graphing engine 78 is available to efficiently providegraphical representations of data to be a part of the response of aservice. This tends to be a particularly useful utility, because many ofthe existing data base management systems have relatively sparseresources for graphical presentation of data.

The combination of Cool ICE engine 76 and repository 80 permits a rathersimplistic service request from internet terminal 54 in dialog format toinitiate a rather complex series of data base management systemfunctions. In doing so, Cool ICE engine 76 emulates an intranet user ofthe data base management system(s) resident on enterprise server 86and/or departmental server 88. This emulation is only made possible,because repository 80 stores sequences of command language statements(i.e., the logic of the service request) and intermediate products(i.e., the state of the service request). It is these functions whichare not available in ordinary dialog on the world wide web and aretherefore not even defined in that environment.

FIG. 5 is a schematic diagram 90 of the software components of the CoolICE system and the software components to which it interfaces in thepreferred mode of the present invention. The client user of the Cool ICEsystem interfaces directly with web browser 92 which is resident oninternet terminal 54 (see also FIG. 4). Web browser 92 is a commerciallyavailable browser operating under a current version of the Windowsoperating system (e.g., Windows 95). The only special requirement of webbrowser 92 is that it be capable of supporting frames.

Web browser 92 communicates with web server software 96 via internetstandard protocol using HTML language using world wide web path 94. Webserver software 96 is also commercially available software, which is, ofcourse, appropriate for to the web server host hardware configuration.In the preferred mode of the present invention, web server software 96is hosted on a Series 2200 mainframe available from Unisys Corporation,from which web server software 96 is readily available.

Cool ICE system software 98 consists of Cool ICE Gateway 100, Cool ICEservice handler 102, Cool ICE administration 104, Cool ICE repository106, and Cool ICE scripting 108. It is these five software modules whichinterface to web server software 96 in HTML using a dialog format andinterface to data base management system interconnect 110 in the commandlanguage of the enterprise data base management system(s) (i.e., ClassicMAPPER in the preferred mode of the present invention).

Cool ICE gateway 100 is the interface between standard, commerciallyavailable, web server software 96 and the internal Cool ICE systemlanguage and logic. As such, Cool ICE gateway 100 translates the dialogformat, incoming HTML service request into internal Cool ICE language.and protocol. Intrinsic in this translation is a determination of theserve category (see also FIG. 4)—that is whether the service request isa native service (i.e., with Cool ICE server-side scripting) or an openservice (i.e., with server-side scripting in another commerciallanguage).

The service request, received from Cool ICE gateway 100, is utilized byCool ICE service handler 102 to request the corresponding object fromCool ICE repository 106 and to open temporary state storage using CoolICE repository 106. Cool ICE scripting 108 is called to translate theserver-side scripting of an open service request as necessary. Cool ICEservice handler 102 sequences through the command language statements ofthe object received from Cool ICE repository 106 and forwards eachcommand in turn to data base management system software 114 foraccessing of the enterprise proprietary data base management system.Cool ICE service handler 102 receives each of the intermediate productsfrom data base management system software 114 and transfers each to CoolICE repository 106 for temporary storage until completion of the servicerequest. Cool ICE service handler 102 retrieves the intermediateproducts from Cool ICE repository 106 upon completion of the servicerequest and formulates the Cool ICE response for transfer to browser 92via web server software 96 and world wide web path 94.

Cool ICE administration 104 implements automatic and manual control ofthe process. It provides for record keeping, for resolution of certainsecurity issues, and for development of further Cool ICE objects.Interconnect 110 and interconnect 112 are software interface modules forcommunicating over the enterprise intranet (see also FIG. 4). Thesemodules are dependent upon the remaining proprietary hardware andsoftware elements coupled to the enterprise intranet system. In thepreferred mode of the present invention, these are commerciallyavailable from Unisys Corporation.

FIG. 6 is a schematic diagram 116 showing the processing of a servicerequest by the Cool ICE system. Screen 118 is the view as seen by theclient or user at an internet terminal (see also FIG. 4). This screen isproduced by the commercially available browser 120 selected by the user.Any such industry standard browser is suitable, if it has the capabilityto handle frames. The language of screen 118 is HTML 124. Hyperlinks 126is used in locating the URL of the Cool ICE resident server. In manyinstances, this will simply be the internet access provider of theinternet terminal, as when the internet terminal is owned by theenterprise and the user is an employee. However, when the user is not anemployee and the internet terminal is not necessarily owned by theenterprise, it becomes more likely that hyperlinks 126 identifies aremotely located server.

Icon 122 is a means of expressly identifying a particular servicerequest. Such use of an icon is deemed to be unique. Additional detailconcerning this use of an icon is available in the above identified,commonly assigned, co-pending U.S. patent application. Window area 128provides for the entry of any necessary or helpful input parameters. Notshown are possible prompts for entry of this data, which may be definedat the time of service request development. Submit button provides theuser with a convenient means to transmit the service request to the webserver in which the Cool ICE system is resident.

Upon “clicking on” submit button 130, screen 118 is transmitted to webserver 136 via world wide web path 132. As discussed above, world wideweb path 132 may be a telephonic dial-up of web server 136 or it mightbe a long and complex path along the internet if web server 136 isremote from the originating internet terminal. Web server 136 is thesoftware which performs the retrieval of screen 118 from world wide webpath 132.

Screen 118 is transferred from web server 136 to Cool ICE gateway 138,wherein it is converted to the internal Cool ICE protocol and language.A browser input file is opened at storage resource 146 via path 140.Thus the initial service request can be accessed from storage resource146 during processing up until the final result is transferred back tothe user. This access readily permits multi-step and iterative servicerequest processing, even though the service request was transferred as asingle internet dialog element. This storage technique also providesinitially received input parameters to later steps in the processing ofthe service request.

Cool ICE gateway 138 notifies Cool ICE service handler 156 that aservice request has been received and logged in. The service requestitself is utilized by Cool ICE service handler 156 to retrieve apreviously stored sequence of data base management system commandstatements from repository 166. Thus, in the general case, a singleservice request will result in the execution of a number of ordered database management system commands. The exact sequence of these commands isdefined by the service request developer as explained in more detailbelow.

Service input parameters 170 is prepared from the service request itselfand from the command sequence stored in repository 166 as shown by path164. This list of input parameters is actually stored in a dedicatedportion of repository 166 awaiting processing of the service request.

Each command statement from repository 166 identified with the servicerequest is sequentially presented to Cool ICE service 168 for processingvia path 160. The corresponding input parameter from service inputparameters 170 is coupled with each command statement via path 176 toproduce an appropriate query of the enterprise data base managementsystem at Cool ICE service 168. After the enterprise data basemanagement system has responded to a given query, the intermediateproducts are stored as entries in HTML document 172 which is also storedin a dedicated portion of repository 166.

After all command statements corresponding to the service request havebeen processed by the enterprise data base management system and HTMLdocument 172 has been completed, the result is provided via path 156 toCool ICE service handler 156 for temporary storage as a browser outputfile in storage resource 154 via path 152. Cool ICE gateway 138 receivesthe browser output file via path 148. The response is converted to HTMLprotocol and transferred by web server 136 and world wide web path 134to be presented to the user as a modified screen (not shown).

FIG. 7 is a pictographic drawing 178 of the development process forcreating a Cool ICE service. HTFML document 180 is created utilizing anycommercially available standard HTML authoring tool (e.g., MicrosoftFrontPage). The resulting HTML document 180 is stored as a normal .HTMfile. This file will be utilized as a template of the service to bedeveloped.

The authoring process moves along path 182 to invoke the administrationmodule of the Cool ICE system at element 184. The new dynamic service iscreated using HTML document 180 stored as a normal .HTM file as atemplate. As HTML document 180 is imported into Cool ICE, sequences ofscript for the beginning and end of the HTML code are automaticallyappended to the service. Required images, if any, are also uploaded ontothe web server (see also FIGS. 5 and 6). The service is edited byinserting additional Cool ICE script, as required. A more detaileddescription of the editing process may be found in Cool ICE User'sGuide, Revision 1.1, available from Unisys Corporation and incorporatedherein by reference.

The completed service script is transferred along path 186 to element188 for storage. The service is stored as an object in the repository(see also FIGS. 5 and 6). Storage is effected within the appropriatecategory 190 as discussed above, along with services 192, 194, and 196within the same category.

The process proceeds along path 198 to element 200 for testing. Toperform the testing, the URL for the newly created service is enteredinto the browser of the internet terminal, if known. The typical URL isas follows:

http://machine-name/ICEGate/Category/Service

If the URL for the new service is not known, a list of the availableservices may be determined from the Cool ICE system by specifying theCool ICE URL as follows:

http;://machine-name/ICEGate

This call will result in a presentation of a menu containing the definedcategories. Selecting a category from the list will result in a menu forthe services defined within that category. The desired service can thusbe selected for testing. Selection of the service by either means willresult in presentation of the HTML page as shown at element 200.

The process proceeds to element 204 via path 202, wherein the HTML pagemay be enhanced. This is accomplished by exporting the HTML documentfrom the Cool ICE administration module to a directory for modification.By proceeding back to HTML document 180 via path 208, the exported HTMLtemplate is available for modification using a standard HTML authoringtool. After satisfactory completion, the finished HTML document is savedfor future use.

FIG. 8 is a diagram showing a comparison between dialog-based structure210 and service-based structure 212. Dialog-based structure 210 is thenorm for the typical existing proprietary data base management system(e.g., Classic MAPPER). The user, normally sitting at a dedicated userterminal, transfers output screen 214 to the data base management systemto request a service. The user terminal and its normally dedicated linkare suspended at element 216 to permit transfer and operation of thedata base management system. The input is validated at element 218,while the user terminal and its normally dedicated link remainssuspended.

The data base management system processes the service request at element220 while the user terminal remains suspended. Output occurs at element222 thereby releasing the suspension of the user terminal. Thus, a truedialog is effected, because one part of the dialog pair (i.e., the userterminal) is suspended awaiting response from the data base managementsystem. This type of dialog is best accomplished in an environmentwherein at least the user terminal (or data base management system) isdedicated to the dialog, along with the link between user terminal anddata base management system.

Service-based structure 212 illustrates one of the basic constraints ofthe world wide web protocol. To ensure that each of the elements on theworld wide web are sufficiently independent to prevent one element fromunduly delaying or “hanging-up” another element to which it is coupledawaiting a response, the communication protocol forces a terminationafter each transmission. As can be readily seen, even the simplestdialog requires at least separate and independent transactions orservices. The first service, Service 224, involves the transmissions ofoutput form 228 from the internet user terminal. This transmission isimmediately and automatically followed by termination 230 to ensureindependence of the sender and receiver.

The second service, Service 226, enables the receiver of output form 228to process the request and output an appropriate response. Thevalidation of the input at element 232, processing 234, and output 236all occur within the receiver of output form 228. Immediately andautomatically, termination 238 follows. Thus, if internet transactionsare to be linked into a true dialog to permit data base managementfunctions, the state must be saved from one service to the next astaught herein.

In the preferred mode of the present invention, the state of a serviceis saved in the repository (see also FIGS. 4 and 5) for use in the nextor subsequent services.

FIG. 9 is a schematic diagram 240 of the preferred mode of the presentinvention showing normal data flow during operation, with specialattention to the state saving feature. Work station 242 is an industrycompatible personal computer operating under a commonly availableoperating system such as Windows 95. Browser 244 is a standard,commercially available web browser having frames capability. Path 248 isthe normal world wide web path between work station 242 and web server254 for the transfer of service requests and input data. These transfersare converted by Cool ICE gateway 256 as explained above and sent toCool ICE service handler 258 via path 266 for disposition.,

The service request for data and/or another function is converted intothe data base management language by reference to the service definitionportion of repository 262 through reference along path 276. The actualcommand language of the data base management system is utilized overpath 286 to access data base 264. The resultant data from data base 264is transferred to Cool ICE administrator 290 via path 288. State manager260 determines whether the original service request requires additionalqueries to data base 264 for completion of the dialog. If yes, theresultant data just received from data base 264 is transferred via path284 to repository 262 for temporary storage, and the next query isinitiated over path 286, and the process is repeated. This is the statesaving pathway which is required to provide the user of the Cool ICEsystem to function in a dialog form over the world wide web.

Upon receipt of the resultant data from the final query of data base264, state manager 260 determines that the service request is nowcomplete. State manager 260 notifies repository 262 via path 280, andthe intermediate products are retrieved from temporary storage inrepository 262 via path 278 and supplied to Cool ICE service handler 258via path 272 for formatting. State manager 260 then clears theintermediate products from temporary storage in repository 262 via path282. The final response to the service request is sent to Cool ICEgateway 256 via path 270 for translation and to browser 244 via path250.

FIG. 10 is a diagram 300 showing storage of a recently received object.The object in this example is created and/or transferred via path 304 asshown. This transfer is in HTML format. The object is transferred toCool ICE administration 306 as shown schematically. For the actual path,see a more detailed explanation above. Cool ICE administration examinesthe object and selects MIME type 308 through utilization of theattributes of the object, as received. This may include actual MIMEtyping or it may involve more diffuse attributes from locally generatedobjects.

Through selection of MIME type, a location 312 is assigned. In thismanner, the storage location of the object within the Cool ICErepository is indicative of the MIME type. Therefore, the MIME type canbe readily appended upon retrieval. An expiration date, if appropriate,is synthesized and entered in column 310. The completed record 314within Cool ICE administration 306 is unique to the object to be stored.

The object, as converted to internal format, is transferred via path 316to repository 320 for storage. The object in the example is storedwithin object storage area 318, which contains only those objects havingthe same MIME type. The object is thus stored in repository 320 forfuture use.

FIG. 11 is a diagram, similar to that of FIG. 10, showing utilization ofthe MIME type and expiration date information for a sample object storedwithin repository 320. Upon request, the object is accessed from storagearea 318 of repository 320. The location of the object is found inlocation column 312 (see also FIG. 10). The object is retrieved via path322. The MIME type and expiration date are both readily available in theappropriate columns within the same record of Cool ICE Administration306. If the object is to be reconverted to HTML format, the MIME type isappended. The corresponding entry in expiration column 310 is checked tosee if the object contains obsolete data. If yes, the transfer is notcompleted. If no, the transfer is made over path 324 in HTML format.

FIG. 12 is a detailed diagram 326 showing the retrieval of an objectstored in accordance with the preferred mode of the present invention. Auser at workstation 328 creates a service request in browser 330requesting the stored object of the present example. The service requestis transferred via path 332 to web server 338 hosting Cool ICE system340.

The service request is converted by Cool ICE gateway 342 as discussedabove. The converted service request is transferred to service handler348 for processing. Because the service request involves access to thestored object of the present example, administration module 364 isnotified via path 362.

Before making the requested access, Cool ICE administration 364 checksthe stored expiration date associated with the stored object of thepresent example. If the expiration date entry shows that the requestedobject contains obsolete information, the object is not requested fromthe repository. However, a diagnostic message is transferred via path360 to service handler 348 indicating expiration of the requestedobject. The diagnostic message is sent to Cool ICE gateway 346 forconversion. The HTML display page containing the diagnostic messageindicating that the requested record has expired is transferred via path334 to web browser 330 of workstation 328.

On the other hand, if Cool ICE administration 364 finds that therequested object has not expired, the access request is transferred viapath 366 to MIME 370 for access of the MIME type and the location. Theaccess request is made of repository 354 via path 358. The requestedobject is accessed from service object storage area 356, the MIME typeis appended, and the data is sent via path 352 to service handler 348for processing. The resultant is transferred via path 350 to Cool ICEgateway 342 for conversion. The resultant as converted to an HTMLdisplay page containing the MIME type information and is transferred viapath 336 to workstation 328.

Having thus described the preferred embodiments of the presentinvention, those of skill in the art will be readily able to adapt theteachings found herein to yet other embodiments within the scope of theclaims hereto attached.

I claim:
 1. In a data processing environment having a user terminalwhich generates a service request coupled to a publicly accessibledigital communications network wherein said user terminal anticipates aresponse to said service request being identified by MIME type andhaving a legacy dialog based data base management system for providingsaid response to said service request wherein said legacy data basemanagement system can not provide said response identified by MIME type,the improvement comprising: server having a gateway providing aninterface between said user terminal and said legacy data basemanagement system responsively coupled to said user terminal via saidpublicly accessible digital communications network and responsivelycoupled to said legacy data base management system wherein said serverincludes an administration module which synthesizes a MIME type codebased only upon and appropriate to said response received from saidlegacy data base management system and appends said MIME type code tosaid response to said service request.
 2. The improvement according toclaim 1 wherein said administration module includes a repository forstoring said MIME type code in a fashion associated with said response.3. The improvement according to claim 2 wherein said publicly accessibledigital communications network is the world wide web.
 4. The improvementaccording to claim 3 wherein said administration module furthercomprises an expiration date checking module which sends a diagnosticmessage to said user terminal if said response is indicated to beexpired.
 5. The improvement according to claim 4 wherein said data basemanagement system is Classic MAPPER.
 6. An apparatus comprising: a. auser terminal which makes a service request and receives a responsecontaining an MIME type; b. a publicly accessible digital communicationsnetwork; c. a server having a gateway providing an interface to saiduser terminal responsively coupled to said user terminal via saidpublicly accessible digital communications network; d. a legacy dialogbased data base management system which generates said response havingno MIME type in response to said service request; and e. anadministration module for synthesizing a MIME type code based only uponand appropriate to said response and appending said MIME type to saidresponse.
 7. The apparatus of claim 6 wherein said administration modulehas storage for said MIME type code in a fashion consistent with saidMIME code.
 8. The apparatus of claim 7 further comprising a module forchecking for expiration of an object corresponding to said servicerequest and sending a diagnostic message whenever said checkingdetermines expiration.
 9. The apparatus of claim 8 wherein said publiclyaccessible digital communications network is the world wide web.
 10. Theapparatus of claim 9 wherein said user terminal is an industrycompatible personal computer having a commercially available webbrowser.
 11. A method of communicating between a user terminalgenerating a service request and a dialog based data base managementsystem honoring said service request comprising: a. transmitting saidservice request from said user terminal; b. converting saidservice-based request by a gateway into an object for execution by saiddata base management system; c. executing said object by said data basemanagement system to produce a resultant having no MIME type code; d.synthesizing a MIME type code based upon and corresponding to saidresultant; e. appending said MIME type to said resultant; and f.transferring said resultant and said appended MIME type to said userterminal.
 12. A method according to claim 11 further comprising storingsaid MIME type code in accordance with and in specific relationship tosaid object.
 13. A method according to claim 12 further comprisinginhibiting said executing, synthesizing, appending, and transferringsteps if said object is obsolete and transferring a diagnostic message.14. A method according to claim 13 wherein said transmitting stepfurther comprises transmitting over the world wide web.
 15. A methodaccording to claim 14 wherein said data base management system furthercomprises Classic MAPPER data base management system.
 16. An apparatuscomprising: a. means for permitting a user to interact with a digitaldata base; b. means responsively coupled to said permitting means forproviding said user with access to a publicly accessible digitalcommunication network via service-based requests; c. means responsivelycoupled to said permitting means for offering dialog based dataprocessing services according to dialog-based requests producing aresponse having no MIME type; and d. means responsively coupled to saidoffering means and said permitting means for synthesizing and appendinga MIME type code to said response from said offering means.
 17. Anapparatus according to claim 16 wherein said publicly accessible digitalcommunication network further comprises the world wide web.
 18. Anapparatus according to claim 17 wherein said appending means furthercomprises means for storing said MIME type code in a fashion appropriateto storage of said response.
 19. An apparatus according to claim 18wherein said offering means further comprises Classic MAPPER data basemanagement system.
 20. An apparatus according to claim 19 wherein saidpermitting means further comprises